Subject |
divide up |
require |
has definition |
have goals |
see also |
has part |
is a subtopic of |
is a kind of |
have advantage |
is an instance of |
determine |
approach to identifying generalizations | | | | | | | 5.8 - The Process Of Developing Class Diagrams | principle | | | |
top-down design | | considerable experience | An approach to design in which one starts with the high-level architecture of the system, then elaborates the design of subsystems until finally designing the low-level details such as the structure of individual classes | - Increasing profit by reducing cost and increasing revenue
- Ensuring that we actually conform with the requirements, thus solving the customers' problems
- Accelerating development, which helps reduce short-term costs, and may also ensure the software reaches the market soon enough to effectively compete
- Increasing qualities such as usability, efficiency, reliability, maintainability, and reusability which can help reduce costs and also increase revenues
| design^2 | user interface design | 9.1 - The Process of Design | design | gives the system being designed a good structure | | how components will be implemented in a system |
top-down approach to identifying generalizations | a complex class, creating new subclasses | considerable experience | | - Increasing profit by reducing cost and increasing revenue
- Ensuring that we actually conform with the requirements, thus solving the customers' problems
- Accelerating development, which helps reduce short-term costs, and may also ensure the software reaches the market soon enough to effectively compete
- Increasing qualities such as usability, efficiency, reliability, maintainability, and reusability which can help reduce costs and also increase revenues
| design^2 | user interface design | 5.8 - The Process Of Developing Class Diagrams | | gives the system being designed a good structure | top-down design | how components will be implemented in a system |